Vcenter Namespaces ResourceQuotaOptionsV1
The Vcenter Namespaces ResourceQuotaOptionsV1 schema represents the resource quota limits which can be applied on the namespace. Refer to for information related to the properties of this object and what they map to.
This schema was added in vSphere API 7.0.0.0.
{
"memory_limit": 0,
"memory_limit_default": 0,
"memory_request_default": 0,
"cpu_limit": 0,
"cpu_limit_default": 0,
"cpu_request_default": 0,
"storage_request_limit": 0,
"pod_count": 0,
"service_count": 0,
"deployment_count": 0,
"daemon_set_count": 0,
"replica_set_count": 0,
"replication_controller_count": 0,
"stateful_set_count": 0,
"config_map_count": 0,
"secret_count": 0,
"persistent_volume_claim_count": 0,
"job_count": 0
}This is equivalent to 'limits.memory' option which is the maximum memory limit (in mebibytes) across all pods which exist in a non-terminal state in the namespace. This value translates to the memory limit on the ResourcePool in vCenter Server created for the namespace.
This property was added in vSphere API 7.0.0.0.
If missing or null, no memory limits are set on the ResourcePool for the namespace.
This represents the default memory limit (in mebibytes) for containers in the pod. This translates to default memory limit in a LimitRange object. Refer for information about LimitRange.
This property was added in vSphere API 7.0.0.0.
If missing or null, no default memory limits are set on containers in the pod.
This represents the default memory request (in mebibytes) for containers in the pod. This translates to default memory request in a LimitRange object. Refer for information about LimitRange.
This property was added in vSphere API 7.0.0.0.
If missing or null, no default memory requests are set on containers in the pod.
This is equivalent to 'limits.cpu' option which is the maximum CPU limit (in MHz) across all pods which exist in a non-terminal state in the namespace. If specified, this limit should be at least 10 MHz. This value translates to the CPU limit on the ResourcePool in vCenter Server created for the namespace.
This property was added in vSphere API 7.0.0.0.
If missing or null, no CPU limits are set on the ResourcePool for the namespace.
This represents the default cpu limit (in MHz) for containers in the pod.
This property was added in vSphere API 7.0.0.0.
If missing or null, no default CPU limits are set on containers in the pod. Refer for information about LimitRange. If specified, this limit should be at least 10 MHz.
This represents the default CPU request (in MHz) for containers in the pod.
This property was added in vSphere API 7.0.0.0.
If missing or null, no default CPU requests are set on containers in the pod. Refer for information about LimitRange. If specified, this field should be at least 10 MHz.
This represents 'requests.storage' option which is the maximum storage request (in mebibytes) across all persistent volume claims from pods which exist in a non-terminal state in the namespace.
This property was added in vSphere API 7.0.0.0.
If missing or null, no storage request limits are set on the namespace.
This represents 'pods' option which is the maximum number of pods which exist in a non-terminal state in the namespace.
This property was added in vSphere API 7.0.0.0.
If missing or null, no pod limits are set on the namespace.
This represents 'count/services' option which is the maximum number of services in the namespace.
This property was added in vSphere API 7.0.0.0.
If missing or null, no service limits are set on the namespace.
This represents 'count/deployments.apps' option which is the maximum number of deployments in the namespace.
This property was added in vSphere API 7.0.0.0.
If missing or null, no deployment limits are set on the namespace.
This represents 'count/daemonsets.apps' option which is the maximum number of DaemonSets in the namespace.
This property was added in vSphere API 7.0.0.0.
If missing or null, no daemonset limits are set on the namespace.
This represents 'count/replicasets.apps' option which is the maximum number of ReplicaSets in the namespace.
This property was added in vSphere API 7.0.0.0.
If missing or null, no replicaset limits are set on the namespace.
This represents 'count/replicationcontrollers' option which is the maximum number of ReplicationControllers in the namespace.
This property was added in vSphere API 7.0.0.0.
If missing or null, no replicationcontroller limits are set on the namespace.
This represents 'count/statefulsets.apps' option which is the maximum number of StatefulSets in the namespace.
This property was added in vSphere API 7.0.0.0.
If missing or null, no statefulset limits are set on the namespace.
This represents 'count/configmaps' option which is the maximum number of ConfigMaps in the namespace.
This property was added in vSphere API 7.0.0.0.
If missing or null, no configmap limits are set on the namespace.
This represents 'count/secrets' option which is the maximum number of secrets in the namespace.
This property was added in vSphere API 7.0.0.0.
If missing or null, no secret limits are set on the namespace.
This represents 'count/persistentvolumeclaims' option which is the maximum number of PersistentVolumeClaims in the namespace.
This property was added in vSphere API 7.0.0.0.
If missing or null, no persistentvolumeclaim limits are set on the namespace.
This represents 'count/jobs.batch' option which is the maximum number jobs in the namespace.
This property was added in vSphere API 7.0.0.0.
If missing or null, no job limits are set on the namespace.